Classification page properties

You are here: About configuring Meridian > Classification page properties

The Classification property page is one of the most important property pages of the Owner Operator environment. The following table describes the purpose of the different properties that appear on the page.

Classification page properties
Name	Description
Region	For customers with multiple sites, locations, or plants, it may be useful to divide them into different regions. This multi-value property can be hidden for customers with only one site. We do not recommend deleting this property. Simply remove it from the page or give it a correct default value. Typical values are geographical continent, country, or region names.
Plant	Physical site, plant, or location names. This multi-value property can be hidden for customers with only one site. We do not recommend deleting this property. Simply remove it from the page or give it a correct default value. Typical values are city or plant names.
Discipline	The engineering discipline to which the document belongs. Typical values are P&ID, Electrical, Structural, Piping, and Architectural.
Functional location	A logical division of a site or plant. This is a physical location within a site or plant. This property can be configured as either main and sub-areas or as names and codes or abbreviations. Some customers may not have function locations at all. In that case, the property may be hidden or removed from the page. This property is almost always renamed.
Area	A logical sub-division of Functional location. This is a physical location within a site or plant. This property can be configured as either main and sub-areas or as names and codes or abbreviations. Some customers may not have function locations at all. In that case, the property may be hidden or removed from the page. Typical values are numeric or alphanumerical codes.
Class	The document class for an asset document. The class is typically a sub-category of the Discipline. Some customers may not have function locations at all. In that case, the property may be hidden or removed from the page.
Document sequential number	The sequential number part of a document name without additional letters or encoding.
Document name	The documents filename or display name is typically derived from this property.
Title lines	Descriptive information about a document. Four different lines can be used that together form the description.
Stamp	A status stamp independent of the workflow, typically only valid for released documents and describes the status of a document when it is not under revision.
Sheet size	The size of paper on which the document can be printed.
Sheet scale	The scale of a drawing.
Alternative Name	Alternative names under which a document is known. This could be former names or 3^rd party (for example, vendor or customer) names.
Vendor	The name of a third party from which a document was received.
Media	The main media for this document. Typical values are Electronic, Paper, Microfiche, and Not Available.
Initial Project	The initial project in which a document was created.
Latest Project	The last design project in which a document was modified.

Classification page properties

Name

Description

Region

For customers with multiple sites, locations, or plants, it may be useful to divide them into different regions. This multi-value property can be hidden for customers with only one site. We do not recommend deleting this property. Simply remove it from the page or give it a correct default value. Typical values are geographical continent, country, or region names.

Plant

Physical site, plant, or location names. This multi-value property can be hidden for customers with only one site. We do not recommend deleting this property. Simply remove it from the page or give it a correct default value. Typical values are city or plant names.

Discipline

The engineering discipline to which the document belongs. Typical values are P&ID, Electrical, Structural, Piping, and Architectural.

Functional location

A logical division of a site or plant. This is a physical location within a site or plant. This property can be configured as either main and sub-areas or as names and codes or abbreviations. Some customers may not have function locations at all. In that case, the property may be hidden or removed from the page. This property is almost always renamed.

Area

A logical sub-division of Functional location. This is a physical location within a site or plant. This property can be configured as either main and sub-areas or as names and codes or abbreviations. Some customers may not have function locations at all. In that case, the property may be hidden or removed from the page. Typical values are numeric or alphanumerical codes.

Class

The document class for an asset document. The class is typically a sub-category of the Discipline. Some customers may not have function locations at all. In that case, the property may be hidden or removed from the page.

Document sequential number

The sequential number part of a document name without additional letters or encoding.

Document name

The documents filename or display name is typically derived from this property.

Title lines

Descriptive information about a document. Four different lines can be used that together form the description.

Stamp

A status stamp independent of the workflow, typically only valid for released documents and describes the status of a document when it is not under revision.

Sheet size

The size of paper on which the document can be printed.

Sheet scale

The scale of a drawing.

Alternative Name

Alternative names under which a document is known. This could be former names or 3^rd party (for example, vendor or customer) names.

Vendor

The name of a third party from which a document was received.

Media

The main media for this document. Typical values are Electronic, Paper, Microfiche, and Not Available.

Initial Project

The initial project in which a document was created.

Latest Project

The last design project in which a document was modified.

If a customer needs any of these properties, we highly recommend renaming them to the customer's naming standard. Do not create similar properties with similar or identical functionality as this would require modification of every aspect of the environment, including tools, reports, navigation views, import templates, and scripting. Renaming properties' display names is safe. An end user only sees the display name of properties and this keeps the environment easy to identify for those familiar with it.

Related concepts

Lookup list properties

Object tag properties

Default property values


	BlueCielo Meridian REFSYS 2012 Configuration Guide \| BlueCielo ECM Solutions